Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@core/ai-commit-msg/skills/ai-commit-msg/SKILL.md`:
- Around line 26-49: The numbered steps in SKILL.md use incrementing prefixes
(2., 3., 4.) but must use the "1." repeated style to satisfy MD029; update the
ordered list so each item starts with "1." (e.g., the lines describing husky
install, creating `.husky/prepare-commit-msg`, and creating
`ai-commit-msg.config.ts`) so the three list entries use "1." as their prefix
while keeping the existing content and code blocks unchanged.

In `@core/astro-iconify-svgmap/skills/astro-iconify-svgmap/SKILL.md`:
- Around line 27-53: Update the ordered list to "1/1/1" style by changing the
numeric prefixes for the subsequent steps so every list item starts with "1.";
specifically replace the leading "2." in the line starting with "2. Add to
`astro.config.mjs`:", the leading "3." in "3. Import the virtual module in your
base layout (this activates the Vite plugin):", and the leading "4." in "4. Use
icons in any `.astro` component:" to "1." so all ordered items use "1." as the
prefix.

In `@core/multipublish/skills/multipublish/SKILL.md`:
- Around line 153-157: The fenced code block showing the directory tree in
SKILL.md (the block containing "packages/my-pkg/ ... deno.json jsr.json") lacks
a language identifier; update that code fence to include a language tag such as
text (or tree) so it reads ```text at the start of the block to satisfy
markdownlint MD040 and ensure consistent rendering.

In `@core/typed-env/skills/typed-env/SKILL.md`:
- Around line 65-69: The example snippet imports generateExample but then calls
env.generateExample, which is inconsistent; update the snippet so the import and
call match by either importing the env object (e.g., import env from './env' and
call env.generateExample('.env.example')) or call the imported function directly
(generateExample('.env.example')); ensure the symbols in the snippet reference
the same identifier (generateExample or env) to make the example valid.

In `@core/typed-events/skills/react-typed-events/SKILL.md`:
- Around line 19-21: The first-line heading rule is violated because the
sentence "This skill builds on `typed-events`..." appears before the top-level
heading "typed-events — React" in SKILL.md; move the H1 ("# typed-events —
React") to be the very first line of the file and then place the introductory
sentence(s) about building on `typed-events` immediately after that heading so
the file satisfies markdownlint MD041/first-line-heading.